2016-01-25 - 24470 - Spec - Inbound Delivery creation Program Changes Performance Improvement #sncsup #SNCProject

SPECIFICATIONS

2016-01-25-Spec-24470-Inbound Delivery Program Changes

Purpose

Enhance the Inbound Delivery creation program to improve the performance.

Admin Info

Purpose	Enhance Inb Delivery Program
Requested By	Jingsha
Spec Created By	Adithya
Spec Created Date	01/26/2016
Spec QA by	Adithya
Objects	ZSNC_INBOUND_DELV
Document Status	Complete

Estimates

Sl.No	Activity	Estimation in Hours
1	Research
2	Documentation	08
3	Development/ Config	12
4	Unit test in DEV	16
5	Unit test in QUA
6	Other activity
	TOTAL	36

References

Prior Tickets

[Provide links of prior associated Spec / Break Fix BOSS document(s)]
2015-12-27 - 23845 - Service Request - SNC Inbound Delivery

Documents

[Attach any document(s) received for the requirement(s)]

Spec Changes

[List the changes made to program after the approval of the original requirement along with the Date on which the change request was received and the name of the initiator]

Sl.	Change Details	Requested By	Requested On	Notes if any

Functional Requirement

Purpose/WHY:

[Explain the purpose of the project and the reason why this requirement has come]
The Inbound Delivery Creation Program is taking long time to process in the production system, hence the program has to be changed so that the POs has to be fetched from EKES.

In Scope:
[List the activities to be included in scope]
POs for which ZN/ZB are updated in mentioned dates.

Out of Scope:

[Out of scope activities]
If Inb Delivery is deleted for any PO, Inb Delivery may not be created automatically by program if date range is given in input.

Solution Summary

[Discuss this section with Requester and get approval prior to beginning work]
Enhance the program to make it fetch the SNC POs and process the POs faster to create Inb Delivery.

NE has Suggested to Add EKES and get the List of POs for which confirmations are updated on the given date (input) and pass those list of Pos to EKKO and do the normal cycle from EKKO-EKPO-EKET-EKES and create the Inbound Delivery.
Add New filed in the Input screen of the Program "Confirmation Updated From & To, so as the when the date range input is given the POs which are updated only with the confirmation key will be fetched and processed.
If the date range is not given in the input then skip the EKES step and it shall create the Inb Deliveries checking all the SNC pos and then create for those which are required.

Call with Jingsha on 01/27/2016
In the program is run in by giving the date range as input go to EKES for PO Search and then filter Nb or Z3NB in EKKO and then go to EKPO and look for confirmation key which is ZSNC.
If no date range is given input skip ekes first step and do the normal process. When there is no dates input any of the other field Vendor or PO number input is mandatory.

Two new fields are to be given in the input:
1. PO Status updated From To_
2. Confirmation Key _ (ZSNC - Which is from EKPO)

Chat with Jeff on 02/03/2015:
If no POs are there for Inb Deliveries to be created, if the Inb Delivery creation job is scheduled in the background the job shall not go to Cancelled status instead the job shall be finished with the information in the spool "No POs with valid confirmation category"

Call with Jingsha on 02/05/2016.
The new input field "Confirmation Key shall be a mandatory field and default to ZNSC"
Note: Please do not run this program with confirmation key ZNEC only run it with ZSNC.

Test Plan
[List test scenarios/cases to be executed here]

Test ID	Test Scenario	Expected Results
INB001	Update Sewing "ZN" Confirmations for Z3NB POs and Publish the PO "ZB" for NB POs and give the date range in the Input of the Program and execute the program.	Z3NB: One Inbound delivery per SO-PO combination for Z3NB POs if the confirmations are updated in the input date range given NB: One Inbound Delivery per purchase requisition shall be created, If Purchase req is not there one Inb delivery for whole PO. (if the confirmations are updated in the input date range given)
INB002	Create multiple sales orders (TAS) and convert the same into single PO and update the confirmation key for all items in the PO.	Create inbound deliveries one per sales order if the confirmations are updated in the input date range given
INB002	Update ZN for a third Party Order for all lines of a PO which is having one sales order	One Inbound Delivery has to be created for the PO SO Combination.
INB003	Create a sales order and 3 Purchase Orders for that sales order, in each Purchase Order there shall be other sales orders also.	One Inbound Delivery shall be created for one PO-SO Combination. SO1-PO1 - One Inb Delivery1 SO1-PO2 - One Inb Delivery2 SO1-PO3 - One Inb Delivery3
INB004	Update ZB for the all lines in a Z3NB Quick Turn PO and a NB Quick turn PO and execute the program by giving the date range as input	Inbound Delivery shall be created for PO-SO combinations for Z3NB PO and also for NB PO.
INB005	Performance Testing: Before Program Change: Create the Inbound Deliveries for at least 10 POs and check the time After Program Change: Create the Inbound Deliveries for same number of POs which performance test done before program change	Peformance is expected to be improved
INB006	Execute the Program with out giving the date range in the input	The Program shall consider all the POs and create the Inb Delivery for the ones which has to be created.

Solution Details

[Provide complete technical details for configuration or programming here]
Modify the program:
1. To provide an option to enter the Confirmation Updated Date Range in the Selection (ERDAT)
2. In case Confirmation Updated Date is filled then fetch the data from EKES table based on the Given Date and Confirmation Category (EBTYP - ZB/ZN) and proceed to the next tables
EKKO-EKPO-EKET-EKES and create the Inbound Delivery
3. In case Confirmation Updated Date is not filled then will fetch the data from tables EKKO-EKPO-EKET-EKES and create the inbound deliveries.

Issues

[List Issues / Bugs identified in configuration or development]
4500108576
If a Purchase order is having two lines and one sales order for both the lines, both the lines are having different confirmation keys ZNEC & ZSNC, Inb Delivery would be created for the one line which is having ZSNC confirmation key.
All SNC POs have to be created with ZSNC confirmation key and Non SNC POs must not have ZSNC confirmation key.